home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c
- Path: news.sprintlink.net!eskimo!news
- From: mag@eskimo.com (mAg)
- Subject: Re: Are libraries Compiler dependent?
- X-Nntp-Posting-Host: tia1.eskimo.com
- Message-ID: <DLD52t.IAp@eskimo.com>
- Sender: news@eskimo.com (News User Id)
- Organization: *.*
- X-Newsreader: WinVN 0.93.10
- References: <rmhanson.82.30FAD0B2@students.wisc.edu>
- Date: Thu, 18 Jan 1996 06:08:52 GMT
-
- In article <rmhanson.82.30FAD0B2@students.wisc.edu> (Mon, 15 Jan 1996 22:09:55 GMT),
- rmhanson@students.wisc.edu says :
- >
- >Just as the title says are libraries dependant?
- >
- >right now I just use the standard libraries accompaning the compiler, but
- >I want to use new functions that I picked up that are in a seperate Lib named
- >graph.lib.
- >
- >I was under the impression that I could take a lib created by a different
- >compiler and run it w/ mine....
- >
- >or do I have to take the seperate *.c files and create my owm w/ its own *.h?
- >
- >thanx
- >ryan
-
- If you stick to standard C your source code will be portable, however Executables are not
- portable. You need to compile the source for the other CPU/OS using the compiler for that
- configuration.
-
- Using some other LIB file will work for that specific compiler/CPU/OS, and it may even work
- for some other compilers on the same CPU/OS but will most certainly will not work on other
- machine/OS.
-
- Only C source is guaranteed to be portable if you stick to standard C.
-
- BTW C language has no comcept of graphics.
- --
- /* --------------------------------------------------------
- MAG@ESKIMO.COM
- http://www.eskimo.com/~mag/index.html
- ***********************************************************
- To understand recursion one must first understand recursion
- ***********************************************************
- -------------------------------------------------------- */
-
-